Chapter 1 IR829 Roadway Broker Installation

Upgrade the IR829 Software

Upgrade the IR829 IOS Software

1. Download IR829 IOS version 15.7(3)M1 and transfer it to the IR829 flash via HTTP, TFTP, etc. For example, hosted from a local web server:

copy http://load.vcxz.org/829/ir800-universalk9-bundle.SPA.157-3.M1.bin flash:

This documentation assumes you know the basics of working with the IOS CLI, like entering privileged mode via enable and how to configure a temporary IP address on the router in order to allow for a copy command like the one above to work over your local network. It also assumes you know how to load IOS image files from a local web server or use a TFTP client in place of the HTTP transfer above.

2. Upgrade the IOS software

bundle install flash:ir800-universalk9-bundle.SPA.157-3.M1.bin

3. Save the configuration and reboot the IR829 to finish the upgrade process

write mem
reload

It doesn’t matter whether you reload the internal AP when prompted

During the next boot cycle the system will reboot itself multiple times to upgrade firmware components. It’s safe to ignore warnings about multiple attempts to boot - these are normal.

Eventually you’ll get a prompt that says Press RETURN to get started! and you can move on to upgrading the AP803

Upgrade the AP803 Autonomous IOS Software

1. Download AP803 autonomous IOS version 15.3(3)JG1
2. Set any IP address on the wlan-ap0 interface

conf t
int wlan-ap0
 ip addr 10.0.0.255 255.255.255.255
end

This can really be any IP address. It will only be used to session into the AP803 this one time to upgrade the IOS. We’ll overwrite this with the permanent configuration later.

3. Session into the AP803

service-module wlan-ap 0 session

When prompted, log in as cisco / cisco

4. Upgrade the IOS software. For example, hosted from a local web server:

archive download-sw /overwrite /reload http://load.vcxz.org/829/ap1g3-k9w7-tar.153-3.JG1.tar

5. Once the automatic reload happens and the AP803 boots using the new IOS version you can escape back to the 829 IOS console with CTRL-^ then x and disconnect the AP803 console with discon

Load the DOT Demo Kit IR829 Configuration

1. Download one of the IR829 configuration load files here
2. Review the configuration, making sure to update any desired SSIDs and PSKs and to enable the WGB uplink configuration in the AP803 section if that is how the kit will connect to the Internet
3. Copy and paste it into the IR829 console in chunks
4. Restart IOx to take the updated configuration into account

guest-os 1 restart

5. Wait until show iox host list detail shows that IOx is running again before moving onto the next section

Deploy EFM to IOx

1. Download the IOx EFM 1.2.0 bundle .zip file here
2. Unzip EFM-1.2.0.zip
3. Connect to the demo1-devices SSID (if not changed above) hosted by the IR829
4. Browse to https://10.11.1.194:8443 and log in as cisco / C!sc0123
5. Select the System Setting tab and click the Disable Application Signature button
6. Select the Applications tab and click the Add New button
   1. Set the Application Id to efm
   2. Click the Choose File button
   3. Select the package.tar file in the unzipped EFM-1.2.0/iox-1.2.0/efm_x86_64 folder and click Open
   4. Click OK and wait for the Successfully Deployed message before continuing (it will take a few minutes)
7. Click Activate, which will automatically bring you to the Resources tab
   1. Under Serial Access Configuration choose:

• Serial Adaptor 0: async0
• Serial Adapter 1: async1
• Serial Adapter 2: GPS NMEA

2. Stay with the defaults for the Resource Profile and Network Configuration sections
3. Click Activate
4. Select the Applications tab again and click the Start button under the efm application

Connect the IOx EFM Broker to the Upstream EFM Broker

1. Download the ioxclient utility here and unzip it
2. Open a command terminal and run ioxclient

The first time ioxlient is run it will ask some defaults that make subsequent use of the utility easier.

• Enter what you want for your organization name and URL
• Enter 10.11.1.194 for the IOx platform IP address
• Hit Enter to accept the default port 8443
• Enter cisco as the authorized user
• Enter C!sc0123 as the password
• Hit Enter to accept the defaults for the local repository path, URL scheme, and API prefix
• Enter 22 as the IOx platform’s SSH port
• Hit Enter to accept a blank RSA key and again to accept a blank x.509 certificate

3. Run ioxclient app console efm
   1. Hit Enter to accept the SSH key fingerprint
   2. Hit Enter to show the login prompt and log in as root with no password

You are now logged into the Linux console of the IOx EFM application

4. Enter the following commands, substituting the correct upstream broker information as appropriate to your demo setup. You will likely want to change the following:

• The filename and "name" value to match the upstream broker name
• The "brokerName" to match your kit’s broker name (e.g. efm-roadway1)
• The "url" to match the upstream broker URL

cd /data/appdata/upstream
tee efm-region2 << EOT
{"name": "efm-region2", "brokerName": "efm-roadway1", "url": "https://efm-region2.iotvehicle.net:8443/conn", "enabled": "true"}
EOT

• Type exit to exit the login session
• Hit <ctrl-]> to exit the IOx app console

5. Restart the EFM IOx app with ioxclient app restart efm to ensure the upstream configuration changes take effect

On to Chapter 2 Regional Broker Installation